Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@components/chat_widget/src/components.d.ts`:
- Line 108: The declaration of the component property versionNumber conflicts
with its `@internal` documentation in ocs-chat.tsx (around the `@Prop`() on the
versionNumber field) — decide whether it should remain part of the public API or
be private; if it should be internal-only, remove the `@Prop`() decorator from the
versionNumber field in ocs-chat.tsx and convert it to an
internal/service-managed property (or use a private class field/getter) and
update any tests and API request usages accordingly, then regenerate the
component types so components.d.ts no longer exposes versionNumber; if it should
stay public, update the JSDoc/comment to explicitly state "for internal
consumers only" and keep the `@Prop`() but regenerate types to reflect the
clarified documentation.

In `@components/chat_widget/src/components/ocs-chat/ocs-chat.tsx`:
- Around line 504-514: Add unit tests for the new character-limit feature in the
OcsChat component: create tests that render OcsChat (or its exported
component/test wrapper) and exercise the message input and send flow for three
cases — (a) when maxCharLimit is unset: assert no character counter is rendered
and sendMessage (triggered via send button or calling sendMessage) succeeds/does
not block; (b) when message length equals maxCharLimit: assert the counter shows
a warning state (e.g., warning class or text), and send remains enabled; (c)
when message length exceeds maxCharLimit: assert the counter shows an error
state, the send button is disabled, and sendMessage does not proceed. Use the
component name OcsChat, the sendMessage handler (or send button/data-testid),
the input change handler (or message input element), and the character counter
element/data-testid to locate DOM nodes; use Jest + React Testing Library
patterns (render, fireEvent/change, getByTestId/queryByText, expect) to
implement assertions.

In `@templates/chatbots/chat/web_chat.html`:
- Line 38: The template uses max_char_limit but neither chatbot_session_view()
nor _chatbot_chat_ui() includes it in the context, so add max_char_limit into
the version_specific_vars dict returned by both functions (ensure the key name
matches the template attribute: max_char_limit) and propagate any existing
config/default logic used for character limits; then add unit tests that render
web_chat.html via both chatbot_session_view and _chatbot_chat_ui to assert the
attribute is present in the rendered HTML and an integration/widget test that
enforces the char limit when sending messages.

---

Nitpick comments:
In `@components/chat_widget/src/components/ocs-chat/ocs-chat.tsx`:
- Around line 1765-1769: Add accessible live region and link it to the textarea:
update the character counter element (give it id "ocs-char-counter") to include
aria-live="polite" and role="status" so screen readers announce updates, and on
the textarea component (referenced where this.maxCharLimit is used) add
aria-describedby={this.maxCharLimit != null ? 'ocs-char-counter' : undefined}
and aria-invalid={this.messageTooLong || undefined} so the counter is announced
and the over-limit state is exposed to assistive tech.
- Around line 1798-1807: The send-button currently only sets title for the
composer.messageTooLong state so other disabled reasons (uploading, typing,
empty input) are not conveyed to assistive tech; update the send button (the
component rendering the button where title is set) to also reference an
aria-describedby ID that points to a live region or descriptive element that
reflects composer.messageTooLong and other disable reasons (e.g., uploading,
typing, empty input), or ensure the counter element exposing
composer.messageTooLong has aria-live so screen readers announce the reason;
specifically, add an aria-describedby attribute on the send button pointing to
the existing counter/error element (or create a visually-hidden live region) and
ensure that element's content is updated when composer.messageTooLong or other
disable conditions change so keyboard/AT users are informed.